Repository navigation
feat(agentic): migrate recipe-performance and add paired device measurement - #225
Open
abretonc7s wants to merge 12 commits into
Open
abretonc7s wants to merge 12 commits into
abretonc7s wants to merge 12 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrate the existing
recipe-performanceworkflow into the agentic domain and add Mobile bottleneck diagnosis and paired proof for devices, simulators and emulators.Validation: seven focused kit checks, Extension collector checks and repository CI pass. Retained raw reports reproduce byte for byte. A failing-first deep-stack regression and real-profile replay cover CPU rendering without interpreter tuning.
Blind iOS-simulator validation on this head produced a lazy funding-hook optimization. Four alternating restarted blocks, n=10 per state per direction: first-JS-frame delay improved 17.7% Long / 17.9% Short; opening improved 14.6% / 16.2%, with block separation and better p75/readiness. 246 focused product tests and the 39-step recorded control proof pass.
Long's post-open maximum JS gap worsened; total post-open blocking overlapped. No native/compositor FPS claim. The formal product visual gate remains pending; the local demonstration is unpublished. A self-contained HTML results page includes the actual flame image, code diff, wall time and comparison with the prior physical-device result.